﻿<%@ Page language="C#" MasterPageFile="~masterurl/default.master" Inherits="Microsoft.SharePoint.WebPartPages.WebPartPage, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<asp:Content ID="Content1" ContentPlaceHolderId="PlaceHolderAdditionalPageHead" runat="server">
     <script type="text/javascript" src="../Scripts/jquery-1.8.0.min.js"></script>
      
     <script type="text/javascript" src="/_layouts/15/sp.runtime.debug.js"></script>
     <script type="text/javascript" src="/_layouts/15/sp.debug.js"></script>  
    <script type="text/javascript" src="../Scripts/Help.js"></script> 
</asp:Content>

<asp:Content ID="Content2" ContentPlaceHolderId="PlaceHolderMain" runat="server">
     <div>
        <a href="PhotoHelp.aspx">Photo help</a>
         <br />
         <a href="SettingsHelp.aspx">Settings help</a>
    </div>   
    
    <h1 id="FullScrollableH1">SharePoint 2013 Photo Gallery Spotlight Instructions</h1>
    <h2 id ="FullScrollableH2">Step 1: Alter the Settings List</h2>
    <p>
        This project has one app part (full.aspx), typically that should be placed on a home page. So make your first entry to look like this:
        <br />
            <b><i>&lt;View&gt;&lt;Query&gt;&lt;Where&gt;&lt;Eq&gt;&lt;FieldRef Name='SPGPublish' /&gt;&lt;Value Type='Lookup'&gt;Yes&lt;/Value&gt;&lt;/Eq&gt;&lt;/Where&gt;&lt;/Query&gt;&lt;RowLimit&gt;10&lt;/RowLimit&gt;&lt;/View&gt;</i></b>
        <br />
        A more complicated example:
        <br />
          <b><i>  &lt;View&gt;&lt;Query&gt;&lt;Where&gt;&lt;And&gt;&lt;Eq&gt;&lt;FieldRef Name='SPGPublish' /&gt;&lt;Value Type='Lookup'&gt;Yes&lt;/Value&gt;&lt;/Eq&gt;&lt;BeginsWith&gt;&lt;FieldRef Name='ContentTypeId'/&gt;&lt;Value Type='Text'&gt;0x01010200811A6DA9EF1447C2906335539FBEEF24&lt;/Value&gt;&lt;/BeginsWith&gt;&lt;/And&gt;&lt;/Where&gt;&lt;/Query&gt;&lt;RowLimit&gt;10&lt;/RowLimit&gt;&lt;/View&gt;</i></b>
    </p>
    <p>
            The web part on full.aspx is going to look for an entry on the settings page with the Full Scrollable Instance set to: "Home". (no quotes) You can verify this by looking at Full.js. The purpose of doing this is that if you ever
        want to have multiple webparts that behave different or look different, just create a new aspx and js file and have the new webpart look at a new entry in the Settings list. 
        With this example, it is possible to have multiple Full Scrollables that might be slightly different. Each location that it is used can be set in the Full Scrollable Instance column. If the web part is identical, then
        just have one entry in the Settings page. 
        <br />
        If that level of abstraction is not good enough for you, then another content type entitled 'Mini Scrollable' was attached to the Settings list. Nothing at this moment is using the Mini content type. 
        <br />
        Setting the Display Thumbnails to anything other than '3' means that you will need to do massive changes to the CSS. Why three? (zero, one, two, three) Get it?
    </p>
    <div id="settingsDiv">

   </div>
    <br />
    <br />

    <h2 id ="H1">Step 2: Upload Photos List</h2>
    <p>
        Upload photos to the gallery. SPG Publish is a yes/no column, including this in your caml query will allow you to display specified photos in the web part        
    </p>
    
</asp:Content>
